Automated PR Review (Experimental)

Thank you for your contribution! You can join our Discord server. It's a great place to connect with fellow contributors and stay updated with the latest developments. Thank you once again.

Required Fixes

• Fix template ID to match the filename (should be CVE-2025-5287).
• Ensure tags are comma-separated without spaces (change likes,dislikes,wordpress,plugin,wp-plugin,unauthenticated,sqli,cve,cve2025,cve-2025-5287 to likes,dislikes,wordpress,plugin,wp-plugin,unauthenticated,sqli,cve,cve2025,cve-2025-5287).

Other Suggestions

• Consider adding more unique matchers to enhance the reliability of the template. For instance, including a response body matcher could further validate the successful exploitation of the vulnerability.
• Including a unique endpoint or message in the body, in addition to the matcher for duration, could help reduce false positives.
• Remediation information is good to include, but you might want to clarify if this is a recommended action or just an advisory.
• Make sure to format the YAML correctly using yamllint to catch indentation issues or trailing spaces before final submission.

I am an AI Template bot, and the team will review the PR shortly.

Also I would have set the sleep timer to be higher than 3 but I ran into a strange issue with the sleep-based SQLi. I tried to set the sleep timer to higher than 3, but something was going on with my Nuclei 3.4.5 client. 2 HTTP requests were getting sent and scans were taking 21 seconds to complete when the sleep timer was set to 5. Using sleep(3) the scan took 9 seconds.
It looks like someone had a similar issue: https://discord.com/channels/695645237418131507/1312897172928466964/1312897172928466964

I updated the template ID to match the file name. I made sure that the tags have no spaces in them too